<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
		<title>overview</title>
		<link type="text/css" rel="stylesheet" href="PLUGINS_ROOT/org.polarsys.capella.doc/html/styles.css"/>
	</head>
	<body>
		<h2 id="Overview">Overview</h2>
		<p>There is two scenarios for migration:</p>
		<ul>
			<li>New Capella version: When a new version of Capella is available, the viewpoint data may need to be migrated.</li>
			<li>New viewpoint version: Within the current version of Capella, when a new version of a viewpoint is available, the viewpoint can be updated to a new version. In this case the viewpoint data may need to be migrated.</li>
		</ul>
		<p>Version numbers follow the usual eclipse convention: major.minor.micro.qualifier For example: 1.1.0.20161004114119
			When a viewpoint is updated in the platform, if its version major or minor number is upgraded the existing models will need a migration. </p>
		<p>The migration is orchestrated by Capella in both cases.</p>
		<p>See 
			<a href="/wiki/../help/topic/org.polarsys.capella.ui.doc/html/First%20steps%20with%20Capella/3.5.%20How%20to%20migrate%20Capella%20projects.html" title="../help/topic/org.polarsys.capella.ui.doc/html/First%20steps%20with%20Capella/3.5.%20How%20to%20migrate%20Capella%20projects.html">How to migrate Capella projects</a> <span class="github-link">
			<a href="/wiki/../../../org.polarsys.capella.ui.doc/html/First_steps_with_Capella/3.5._How_to_migrate_Capella_projects.mediawiki" title="../../../org.polarsys.capella.ui.doc/html/First steps with Capella/3.5. How to migrate Capella projects.mediawiki">(online documentation)</a></span>
		</p>
	</body>
</html>